Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1522

reference: 375-tree-1
name: 1522
tree-preservation-order: undefined
375-tpo-1
uprn
address-text
point: POINT (-1.030805 50.884625)
geometry: MULTIPOLYGON (((-1.030734 50.884618,-1.030737 50.884632,-1.030747 50.884644,-1.030763 50.884655,-1.030782 50.884661,-1.030804 50.884663,-1.030826 50.884661,-1.030846 50.884655,-1.030862 50.884645,-1.030873 50.884633,-1.030876 50.884619,-1.030873 50.884605,-1.030863 50.884593,-1.030848 50.884583,-1.030828 50.884576,-1.030806 50.884574,-1.030784 50.884576,-1.030764 50.884582,-1.030748 50.884592,-1.030738 50.884604,-1.030734 50.884618)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL